home *** CD-ROM | disk | FTP | other *** search
- X-Mailer: MicroDot 1.11beta12 [REGISTERED 00042d] via [DOS/NCBMail V2.21 REL.:160995]
- Message-ID: <xQbkSMD42Daez11@point70.people-s.people.de>
- Organization: People-S Mailboxsystem
- References: <jpstanford-0403961345330001@130.181.6.181>
- X-Gateway: ZCONNECT UU people-s.people.de [DUUCP vom 01.07.1994]
- MIME-Version: 1.0
- Content-Type: text/plain; charset=ISO-8859-1
- Content-Transfer-Encoding: 8bit
- From: j_plewka@people-s.people.de (Joern Plewka)
- Subject: Re: why does everyone have SCSI problems?
- Date: 09 Mar 1996 16:00:02 +0100
- Path: people-s.people.de!j_plewka
- Newsgroups: comp.sys.amiga.hardware
- Distribution: world
-
- jpstanford@space.honeywell.com (Stanford Jeff P) -> "Re: why does everyone have SCSI problems?"
- (04.03.1996)
- > In article <4hdjtu$9vs@galaxy.ucr.edu>, 97jgonza@ultrix.uor.edu (Jeff
- > "Crusader" Gonzales) wrote:
- >
- > > Why does everyone with an A3000 have SCSI problems? My first set of
- > > problems is just starting to occur. I have a FUJITSU 540 meg interally
- > > and an 88 meg syquest externally. I have to reboot and reboot and reboot
- > > before my computer realizes there is a boot drive. I cannot boot if the
- > > syquest is on at bootup, and I get read errors on occassion. What should
- > > I do? I brought it in to TransData in Anaheim and they claimed to fix it
- > > but I still have these problems. What should I do?
- > >
- > > Jeff Gonzales
- > > -> University of Redlands / Johnston Center
- > >
- >
- > First off, not all A3000 owners are having SCSI problems or at least they
- > are not having problems that are not of their own making. My problem
- > occured when I tried to run two harddrives and several interface cards
- > off the A3000 wimpy power supply. I solved this by getting a four bay
- > external chassis for all my SCSI devices other than the primary harddrive.
- > The only other concern, not even severe enough to call a problem, was when
- > I installed AMIX and kept hanging up in the install from tape. This was
- > solved by replacing the -03 WD SCSI Controller with a -07 WD SCSI Controller.
-
- Don`t know these revisions normaly you`ll replace -04 to -08...
- But be sure no cable is bad or brocken...it forces more trouble than the
- chip (my last internal cable workt for me 8 weeks and failed..as usual).
- My problem is changing drives often...if you do so...take blue connectors
- from T&B or other good products.
-
- > If all else fails, try replacing the WD SCSI controller. It worked for me. ;-)
-
- Be sure you use good cable...there is much trash around.
- Simple printercables are use for SCSI`s 10MHz...failture^2.
-
- All Syquest Drives don`t like Syn-Negoation...don`t aktivate it in Batmem.
- (SCSI-prefs)
-
-
- / no / / AMIGA /
- / MS+ / J_Plewka@Amtrash.comlink.de / is /
- / gAIDS / Plewka_J@Informatik.FH-Hamburg.de / back /
- / / / /
-
-
-
-